Systems and methods for managing small data over a non-access stratum

ABSTRACT

A network device receives an attach request indicating that a user device is attempting a connection associated with a non-access stratum (NAS) and a particular interface, and generates a create session request that includes an indication that the connection for the user device is associated with the NAS and the particular interface. The network device provides, to a serving gateway (SGW) of the network, the create session request that includes the indication, and receives, from the SGW, a create session response that includes rules for handling the connection for the user device that is associated with the NAS and the particular interface, wherein the rules have been generated by a policy and charging rules function (PCRF) of the network. The network device provides, to the user device, an attach accept, that includes the rules, to permit the user device is to connect with the network and to utilize the rules.

BACKGROUND

The Third Generation Partnership Project (3GPP) defined a narrowbandInternet of Things (NB-IoT) as a radio interface. NB-IoT is optimizedfor machine type (e.g., IoT device) traffic, and the NB-IoT radio accesstechnology (RAT) is designed to reduce IoT device costs and to minimizebattery consumption by IoT devices. The NB-IoT is also adapted to workin difficult radio conditions, which is frequent for some IoT devices.Although NB-IoT is an independent radio interface, it is tightlyconnected with the long-term evolution (LTE) standard. Non-AccessStratum (NAS) is a set of protocols in an Evolved Packet System (EPS).The NAS is used to convey non-radio signaling between a user device anda mobility management entity (MME) for a LTE/evolved universalterrestrial radio access network (E-UTRAN) access.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A-1E are diagrams of an example implementation described herein.

FIG. 2 is a diagram of an example environment in which systems and/ormethods, described herein, may be implemented.

FIG. 3 is a diagram of example components of one or more devices of FIG.2.

FIG. 4 is a flow chart of an example process for enabling differentcharging and policy enforcement for small data over NAS and an S11-Uinterface.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The following detailed description of example implementations refers tothe accompanying drawings. The same reference numbers in differentdrawings may identify the same or similar elements.

Data over NAS is a mechanism that provides efficient small data transferby using an existing signaling plane for small data transfer. Data overNAS utilizes signaling radio bearers (SRBs) to carry data from a userdevice to a base station (e.g., an evolved Node B or eNB). The data istransported via the MME by encapsulating the data in NAS protocol dataunits (PDUs). This results in a reduced total number of control planemessages for sending a short data transaction, which, in turn, resultsin reduced signaling and conserves a battery life of the user device.

Current systems (e.g., 3GPP systems) and protocols fail to specifymechanisms to signal, to a policy and charging rules function (PCRF),that NAS is being used to transfer small data. Standards (e.g., 3GPP)define an information element (e.g., a serving public land mobilenetwork (PLMN) rate control) which, if received by the PGW, can notifythe PGW that a connection is for data over NAS. However, thisinformation element is defined for purposes of the MME informing apacket data network gateway (PGW) and a service capability exposurefunction (SCEF) of any local serving PLMN rate control that the servingPLMN intends to enforce for NAS data PDUs. In other words, theinformation element is not defined for purposes of informing the PGWthat data is over NAS and an S11-U interface. In addition, theinformation element is not mandatory since the MME needs to beconfigured to include serving PLMN rate control. As a result, the PCRFis unaware that small data is being transferred over NAS, and cannotapply different charging and quality of service (QoS) policies for thedata transfer.

Some implementations described herein provide a network device thatenables different charging and policy enforcement for small data overNAS and an S11-U interface. For example, the network device may receivean attach request from a base station of a network, wherein the attachrequest may indicate that a user device is attempting a connectionassociated with a NAS and a particular interface. The network device maygenerate, based on the attach request, a create session request thatincludes an indication that the connection for the user device isassociated with the NAS and the particular interface, and may provide,to a serving gateway (SGW) of the network, the create session requestthat includes the indication. The network device may receive, from theSGW and as a response to the create session request, a create sessionresponse that includes rules for handling the connection for the userdevice that is associated with the NAS and the particular interface,wherein the rules have been generated by a policy and charging rulesfunction (PCRF) of the network. The network device may provide, to theuser device and based on the create session response, an attach acceptthat includes the rules, to permit the user device to connect with thenetwork and to utilize the rules based on the create session response.

In this way, the network device may make the PCRF aware that small datais being transferred over NAS so that the PCRF may apply differentcharging and QoS policies for the small data transfer. This may resultin a reduced quantity of control plane messages for sending the smalldata transfer, which, in turn, may result in reduced signaling and mayconserve battery life of the user device.

FIGS. 1A-1E are diagrams of an example implementation 100 describedherein. As shown in FIGS. 1A-1E, a user device 105 (e.g., an IoT device)may wish to access a network that includes a base station 110, amobility management entity device (MME) 115, a home subscriber server(HSS) 120, a serving gateway (SGW) 125, a packet data network gateway(PGW) 130, and a policy and charging rules function (PCRF) 135. Forexample, as shown in FIG. 1A, and by reference number 140, user device105 may establish a connection (e.g., a radio resource control (RRC)connection) with base station 110 of the network. In someimplementations, user device 105 may be attempting the connection withthe network to transfer data over a non-access stratum (NAS) and aparticular interface (e.g., a S11-U interface). In some implementations,user device 105 may support cellular Internet of Things (CIoT) evolvedpacket system (EPS) optimization.

Base station 110 may generate an attach request based on user device 105establishing the connection with base station 110, and may provide theattach request to MME 115. As further shown in FIG. 1A, and by referencenumber 145, MME 115 may receive the attach request from base station110. In some implementations, the attach request may include informationindicating that user device 105 supports CIoT EPS optimization.

As further shown in FIG. 1A, and by reference number 150, HSS 120 mayinteract with user device 105 (e.g., via base station 110 and MME 115)and may determine whether user device 105 is authenticated for using thenetwork. If HSS 120 determines that user device 105 is not authenticatedfor using the network, HSS 120 may deny the attach request and userdevice 105 may be unable to establish the connection with the network.If HSS 120 determines that user device 105 is authenticated for usingthe network, HSS 120 may approve the attach request and the process ofestablishing the connection may continue.

As shown in FIG. 1B, and by reference number 155, MME 115 may provide aninformation request (e.g., an evolved packet system (EPS) sessionmanagement (ESM) information request) to user device 105 based on theattach request, and may receive a response from user device 105 based onthe ESM information request. In some implementations, the response fromuser device 105 may include the ESM information requested in the ESMinformation request. In some implementations, the ESM informationrequest procedure may be used by the network to retrieve ESM information(e.g., protocol configuration options, access point name (APN) controlparameters, and/or the like) from user device 105 during the attachprocedure if user device 105 indicates that user device 105 has ESMinformation that needs to be securely transmitted. The ESM informationrequest procedure may provide privacy for the ESM information ifciphering is enabled in the network.

As further shown in FIG. 1B, and by reference number 160, MME 115 mayperform a location update with HSS 120. In some implementations, alocation update procedure may be utilized between MME 115 and HSS 120 toupdate location information, associated with MME 115, in HSS 120. Theprocedure may be invoked by MME 115 and may be used to inform HSS 120about the identity of MME 115 currently serving user device 105, toupdate MME 115 with user subscription data, to provide HSS 120 withother user data (e.g., user device 105 service capability information),and/or the like.

As shown in FIG. 1C, and by reference number 165, MME 115 may send, toSGW 125, a create session request with an indication that the connectionis intended for the NAS and the particular interface (e.g., the S11-Uinterface). In some implementations, for control plane CIoT EPSoptimization, the create session request may indicate that data fromuser device 105 is to utilize the S11-U interface tunneling of the NAS.In some implementations, MME 115 may provide, to SGW 125 and via thecreate session request, information indicating an address (e.g., anInternet protocol (IP) address) of the S11-U interface associated withMME 115, an address (e.g., an IP address) of MME 115 for downlink dataforwarding by SGW 125, and/or the like. In some implementations, theindication that the connection is intended for the NAS and theparticular interface may be provided by an attribute value pair (AVP)that indicates, to PCRF 135, that the connection is intended for the NASand the particular interface.

As shown in FIG. 1C, and by reference number 170, SGW 125 may forwardthe create session request with the indication to PGW 130. In someimplementations, SGW 125 may forward the create session request with theindication, when the create session request is received from MME 115.PGW 130 may receive the create session request with the indication fromSGW 125, and may perform an IP-connectivity access network (IP-CAN)session establishment procedure with PCRF 135. An IP-CAN is an accessnetwork (e.g., a 3GPP access network) that provides IP connectivity.

As shown FIG. 1D, and by reference number 175, in order to perform theIP-CAN session establishment procedure, PGW 130 may provide a requestmessage (e.g., an initial credit control request (CCR-I) message) withthe indication (e.g., that the connection is intended for the NAS andthe particular interface) to PCRF 135. In some implementations, PGW 130may provide the CCR-I message with the indication to PCRF 135 based onthe create session request received from SGW 125. In someimplementations, PCRF 135 may receive the CCR-I message with theindication, and may determine rules for transferring data over the NASand via the S11-U interface (e.g., by user device 105) based on theCCR-I message and based on the indication. In some implementations, therules may include rules associated with QoS to be applied for PGW 130sessions intended for the NAS over the S11-U interface, rules associatedwith charging policies to be applied for PGW 130 sessions intended forthe NAS over the S11-U interface, policy and charging control (PCC)rules, access point name (APN) control parameters, and/or the like.

As further shown in FIG. 1D, and by reference number 180, PCRF 135 mayprovide a credit control answer (CCA) message, that includes the rulesfor transferring data over the NAS and via the S11-U interface, to PGW130, and PGW 130 may receive the CCA message and the rules. In someimplementations, PCRF 135 may provide the CCA answer and the rules toPGW 130 based on the CCR-I message and based on determining the rules.

As further shown in FIG. 1D, and by reference number 185, PGW 130 mayprovide, to SGW 125, a create session response that includes the rulesfor transferring data over the NAS and via the S11-U interface. In someimplementations, PGW 130 may generate the create session response thatincludes the rules based on the CCA message that includes the rules, andmay provide the create session response with the rules to SGW 125 uponcreation.

As shown in FIG. 1E, and by reference number 190, SGW 125 may providethe create session response with the rules to MME 115, and MME 115 mayreceive the create session response with the rules. In someimplementations, MME 115 may generate an attach accept message based onthe create session response with the rules. In such implementations, theattach accept message may include an attach accept over downlink NASmessage. As further shown in FIG. 1E, and by reference number 195, MME115 may provide the attach accept over downlink NAS message to basestation 110. In some implementations, base station 110 may complete theattach procedure with user device 105 based on the attach accept overdownlink NAS message. In this way, user device 105 may provide data overthe NAS and the S11-U interface, and the network (e.g., MME 115) mayapply differentiated QoS and charging policies to PGW 130 sessionsintended for data over the NAS and the S11-U interface.

In some implementations, the indication that the connection is intendedfor the NAS and the particular interface may be provided via differentinterfaces of the network, such as a S5 interface, a Gx interface,and/or the like. In some implementations, the indication that theconnection is intended for the NAS and the particular interface may beprovided to PCRF 135 based on a packet analysis (e.g., a quantity ofpackets, a quantity of lost packets, and/or the like) performed by PGW130.

In this way, several different stages of the process for enablingdifferent charging and policy enforcement for small data over NAS and anS11-U interface are automated, which may remove human subjectivity andwaste from the process, and which may improve speed and efficiency ofthe process and conserve computing resources (e.g., processingresources, memory resources, and/or the like). Furthermore,implementations described herein use a rigorous, computerized process toperform tasks or roles that were not previously performed or werepreviously performed using subjective human intuition or input. Forexample, currently there does not exist a technique that automaticallyenables different charging and policy enforcement for small data overNAS and an S11-U interface. Finally, automating the process for enablingdifferent charging and policy enforcement for small data over NAS and anS11-U interface conserves computing resources (e.g., processingresources, memory resources, and/or the like) that would otherwise bewasted in attempting to apply different charging and policy enforcementfor small data over NAS and an S11-U interface.

As indicated above, FIGS. 1A-1E are provided merely as examples. Otherexamples are possible and may differ from what was described with regardto FIGS. 1A-1E. The number and arrangement of devices and networks shownin FIGS. 1A-1E are provided as an example. In practice, there may beadditional devices and/or networks, fewer devices and/or networks,different devices and/or networks, or differently arranged devicesand/or networks than those shown in FIGS. 1A-1E. Furthermore, two ormore devices shown in FIGS. 1A-1E may be implemented within a singledevice, or a single device shown in FIGS. 1A-1E may be implemented asmultiple, distributed devices. Additionally, or alternatively, a set ofdevices (e.g., one or more devices) of FIGS. 1A-1E may perform one ormore functions described as being performed by another set of devices ofFIGS. 1A-1E.

FIG. 2 is a diagram of an example environment 200 in which systemsand/or methods, described herein, may be implemented. As shown in FIG.2, environment 200 may include a user device 205, a base station 210, amobility management entity device (MME) 215, a serving gateway (SGW)220, a packet data network gateway (PGW) 225, a policy and chargingrules function (PCRF) 230, a home subscriber server (HSS) 235, anauthentication, authorization, and accounting server (AAA) 240; and anetwork 245. Devices of environment 200 may interconnect via wiredconnections, wireless connections, or a combination of wired andwireless connections.

Some implementations are described herein as being performed within along-term evolution (LTE) network for explanatory purposes. Someimplementations may be performed within a network that is not an LTEnetwork, such as a third generation (3G) network, a fifth generation(5G) network, and/or the like.

Environment 200 may include an evolved packet system (EPS) that includesan LTE network and/or an evolved packet core (EPC) that operate based ona third-generation partnership project (3GPP) wireless communicationstandard. The LTE network may include a radio access network (RAN) thatincludes one or more base stations 210 that take the form of evolvedNode Bs (eNBs) via which user device 205 communicates with the EPC. TheEPC may include MME 215, SGW 220, and/or PGW 225 to enable user device205 to communicate with network 245 and/or an Internet protocol (IP)multimedia subsystem (IMS) core. The IMS core may include HSS 235 and/orAAA 240, and may manage device registration and authentication, sessioninitiation, and/or the like, associated with user devices 205. HSS 235and/or AAA 240 may reside in the EPC and/or the IMS core.

User device 205 includes one or more devices capable of communicatingwith other user devices 205, base station 210, and/or a network (e.g.,network 245). For example, user device 205 may include a mobile phone(e.g., a smart phone, a radiotelephone, etc.), a laptop computer, atablet computer, a desktop computer, a handheld computer, a gamingdevice, a wearable communication device (e.g., a smart wristwatch, apair of smart eyeglasses, etc.), or a similar type of device. Userdevice 205 may send traffic to and/or receive traffic from another userdevice 205 and/or network 245 (e.g., via base station 210, SGW 220,and/or PGW 225).

Base station 210 includes one or more devices capable of transferringtraffic, such as audio, video, text, and/or other traffic, destined forand/or received from user device 205. In some implementations, basestation 210 may include an eNB associated with the LTE network thatreceives traffic from and/or sends traffic to network 245 via SGW 220and/or PGW 225. Additionally, or alternatively, one or more basestations 210 may be associated with a RAN that is not associated withthe LTE network. Base station 210 may send traffic to and/or receivetraffic from user device 205 via an air interface. In someimplementations, base station 210 may include a small cell base station,such as a base station of a microcell, a picocell, a femtocell, and/orthe like.

MME 215 includes one or more devices, such as one or more serverdevices, capable of managing authentication, activation, deactivation,and/or mobility functions associated with user device 205. In someimplementations, MME 215 may perform operations relating toauthentication of user device 205. Additionally, or alternatively, MME215 may facilitate the selection of a particular SGW 220 and/or aparticular PGW 225 to provide traffic to and/or from user device 205.MME 215 may perform operations associated with handing off user device205 from a first base station 210 to a second base station 210 when userdevice 205 is transitioning from a first cell associated with the firstbase station 210 to a second cell associated with the second basestation 210. Additionally, or alternatively, MME 215 may select anotherMME (not pictured), to which user device 205 should be handed off (e.g.,when user device 205 moves out of range of MME 215).

SGW 220 includes one or more devices capable of routing packets. Forexample, SGW 220 may include one or more data processing and/or traffictransfer devices, such as a gateway, a router, a modem, a switch, afirewall, a network interface card (NIC), a hub, a bridge, a serverdevice, an optical add/drop multiplexer (OADM), or any other type ofdevice that processes and/or transfers traffic. In some implementations,SGW 220 may aggregate traffic received from one or more base stations210 associated with the LTE network, and may send the aggregated trafficto network 245 (e.g., via PGW 225) and/or other network devicesassociated with the EPC and/or the IMS core. SGW 220 may receive trafficfrom network 245 and/or other network devices, and may send the receivedtraffic to user device 205 via base station 210. Additionally, oralternatively, SGW 220 may perform operations associated with handingoff user device 205 to and/or from an LTE network.

PGW 225 includes one or more devices capable of providing connectivityfor user device 205 to external packet data networks (e.g., other thanthe depicted EPC and/or LTE network). For example, PGW 225 may includeone or more data processing and/or traffic transfer devices, such as agateway, a router, a modem, a switch, a firewall, a NIC, a hub, abridge, a server device, an OADM, or any other type of device thatprocesses and/or transfers traffic. In some implementations, PGW 225 mayaggregate traffic received from one or more SGWs 220, and may send theaggregated traffic to network 245. Additionally, or alternatively, PGW225 may receive traffic from network 245, and may send the traffic touser device 205 via SGW 220 and base station 210. PGW 225 may recorddata usage information (e.g., byte usage), and may provide the datausage information to AAA 240.

PCRF 230 includes one or more devices, such as one or more serverdevices, capable of providing policy control decision and flow-basedcharging control functionalities. For example, PCRF 230 may providenetwork control regarding service data flow detection, gating, qualityof service (QoS) and flow-based charging, and/or the like. In someimplementations, PCRF 230 may determine how a certain service data flowis to be treated, and may ensure that user plane traffic mapping andtreatment is in accordance with a user subscription profile.

HSS 235 includes one or more devices, such as one or more serverdevices, capable of managing (e.g., receiving, generating, storing,processing, providing, and/or the like) information associated with userdevice 205. For example, HSS 235 may manage subscription informationassociated with user device 205, such as information that identifies asubscriber profile of a user associated with user device 205,information that identifies services and/or applications that areaccessible to user device 205, location information associated with userdevice 205, a network identifier (e.g., a network address) thatidentifies user device 205, information that identifies a treatment ofuser device 205 (e.g., quality of service information, a quantity ofminutes allowed per time period, a quantity of data consumption allowedper time period, etc.), and/or similar information. HSS 235 may providethis information to one or more other devices of environment 200 tosupport the operations performed by those devices.

AAA 240 includes one or more devices, such as one or more serverdevices, that perform authentication, authorization, and/or accountingoperations for communication sessions associated with user device 205.For example, AAA 240 may perform authentication operations for userdevice 205 and/or a user of user device 205 (e.g., using one or morecredentials), may control access, by user device 205, to a serviceand/or an application (e.g., based on one or more restrictions, such astime-of-day restrictions, location restrictions, single or multipleaccess restrictions, read/write restrictions, etc.), may track resourcesconsumed by user device 205 (e.g., a quantity of voice minutes consumed,a quantity of data consumed, etc.), and/or may perform similaroperations.

Network 245 includes one or more wired and/or wireless networks. Forexample, network 245 may include a cellular network (e.g., a fifthgeneration (5G) network, a long-term evolution (LTE) network, a thirdgeneration (3G) network, a code division multiple access (CDMA) network,etc.), a public land mobile network (PLMN), a local area network (LAN),a wide area network (WAN), a metropolitan area network (MAN), atelephone network (e.g., the Public Switched Telephone Network (PSTN)),a private network, an ad hoc network, an intranet, the Internet, a fiberoptic-based network, and/or the like, and/or a combination of these orother types of networks.

The number and arrangement of devices and networks shown in FIG. 2 areprovided as an example. In practice, there may be additional devicesand/or networks, fewer devices and/or networks, different devices and/ornetworks, or differently arranged devices and/or networks than thoseshown in FIG. 2. Furthermore, two or more devices shown in FIG. 2 may beimplemented within a single device, or a single device shown in FIG. 2may be implemented as multiple, distributed devices. Additionally, oralternatively, a set of devices (e.g., one or more devices) ofenvironment 200 may perform one or more functions described as beingperformed by another set of devices of environment 200.

FIG. 3 is a diagram of example components of a device 300. Device 300may correspond to user device 205, base station 210, MME 215, SGW 220,PGW 225, PCRF 230, HSS 235, and/or AAA 240. In some implementations,user device 205, base station 210, MME 215, SGW 220, PGW 225, PCRF 230,HSS 235, and/or AAA 240 may include one or more devices 300 and/or oneor more components of device 300. As shown in FIG. 3, device 300 mayinclude a bus 310, a processor 320, a memory 330, a storage component340, an input component 350, an output component 360, and acommunication interface 370.

Bus 310 includes a component that permits communication among thecomponents of device 300. Processor 320 is implemented in hardware,firmware, or a combination of hardware and software. Processor 320 is acentral processing unit (CPU), a graphics processing unit (GPU), anaccelerated processing unit (APU), a microprocessor, a microcontroller,a digital signal processor (DSP), a field-programmable gate array(FPGA), an application-specific integrated circuit (ASIC), or anothertype of processing component. In some implementations, processor 320includes one or more processors capable of being programmed to perform afunction. Memory 330 includes a random access memory (RAM), a read onlymemory (ROM), and/or another type of dynamic or static storage device(e.g., a flash memory, a magnetic memory, and/or an optical memory) thatstores information and/or instructions for use by processor 320.

Storage component 340 stores information and/or software related to theoperation and use of device 300. For example, storage component 340 mayinclude a hard disk (e.g., a magnetic disk, an optical disk, amagneto-optic disk, and/or a solid state disk), a compact disc (CD), adigital versatile disc (DVD), a floppy disk, a cartridge, a magnetictape, and/or another type of non-transitory computer-readable medium,along with a corresponding drive.

Input component 350 includes a component that permits device 300 toreceive information, such as via user input (e.g., a touch screendisplay, a keyboard, a keypad, a mouse, a button, a switch, and/or amicrophone). Additionally, or alternatively, input component 350 mayinclude a sensor for sensing information (e.g., a global positioningsystem (GPS) component, an accelerometer, a gyroscope, and/or anactuator). Output component 360 includes a component that providesoutput information from device 300 (e.g., a display, a speaker, and/orone or more light-emitting diodes (LEDs)).

Communication interface 370 includes a transceiver-like component (e.g.,a transceiver and/or a separate receiver and transmitter) that enablesdevice 300 to communicate with other devices, such as via a wiredconnection, a wireless connection, or a combination of wired andwireless connections. Communication interface 370 may permit device 300to receive information from another device and/or provide information toanother device. For example, communication interface 370 may include anEthernet interface, an optical interface, a coaxial interface, aninfrared interface, a radio frequency (RF) interface, a universal serialbus (USB) interface, a Wi-Fi interface, a cellular network interface,and/or the like.

Device 300 may perform one or more processes described herein. Device300 may perform these processes based on processor 320 executingsoftware instructions stored by a non-transitory computer-readablemedium, such as memory 330 and/or storage component 340. Acomputer-readable medium is defined herein as a non-transitory memorydevice. A memory device includes memory space within a single physicalstorage device or memory space spread across multiple physical storagedevices.

Software instructions may be read into memory 330 and/or storagecomponent 340 from another computer-readable medium or from anotherdevice via communication interface 370. When executed, softwareinstructions stored in memory 330 and/or storage component 340 may causeprocessor 320 to perform one or more processes described herein.Additionally, or alternatively, hardwired circuitry may be used in placeof or in combination with software instructions to perform one or moreprocesses described herein. Thus, implementations described herein arenot limited to any specific combination of hardware circuitry andsoftware.

The number and arrangement of components shown in FIG. 3 are provided asan example. In practice, device 300 may include additional components,fewer components, different components, or differently arrangedcomponents than those shown in FIG. 3. Additionally, or alternatively, aset of components (e.g., one or more components) of device 300 mayperform one or more functions described as being performed by anotherset of components of device 300.

FIG. 4 is a flow chart of an example process 400 for enabling differentcharging and policy enforcement for small data over NAS and an S11-Uinterface. In some implementations, one or more process blocks of FIG. 4may be performed by a network device, such as a MME (e.g., MME 215). Insome implementations, one or more process blocks of FIG. 4 may beperformed by another device or a group of devices separate from orincluding the network device, such as a base station (e.g., base station210), a SGW (e.g., SGW 220), a PGW (e.g., PGW 225), and/or a HSS (e.g.,HSS 235).

As shown in FIG. 4, process 400 may include receiving an attach requestfrom a base station of a network, the attach request indicating that auser device is attempting a connection associated with a non-accessstratum (NAS) and a particular interface (block 410). For example, thenetwork device (e.g., using processor 320, communication interface 370,and/or the like) may receive an attach request from a base station of anetwork, as described above in connection with FIGS. 1A-2. In someimplementations, the attach request may indicate that a user device(e.g., an IoT device) is attempting a connection associated with anon-access stratum (NAS) and a particular interface (e.g., a tunnelinginterface, such as a S11-U interface). In some implementations, theattach request may include information indicating that the user devicesupports cellular Internet of Things (CIoT) evolved packet system (EPS)optimization.

As further shown in FIG. 4, process 400 may include generating, based onthe attach request, a create session request that includes an indicationthat the connection for the user device is associated with the NAS andthe particular interface (block 420). For example, the network device(e.g., using processor 320, memory 330, communication interface 370,and/or the like) may generate, based on the attach request, a createsession request that includes an indication that the connection for theuser device is associated with the NAS and the particular interface, asdescribed above in connection with FIGS. 1A-2. In some implementations,the indication may include an attribute value pair that indicates theconnection for the user device is intended for the NAS and theparticular interface.

In some implementations, the network device may provide an evolvedpacket system (EPS) session management (ESM) information request to theuser device based on the attach request, and may receive ESM informationfrom the user device based the ESM information request. In someimplementations, when generating the create session request, the networkdevice may generate, based on the ESM information, the create sessionrequest that includes the indication that the connection for the userdevice is intended for the NAS and the particular interface. In someimplementations, the network device may perform a location update,associated with the network device, with a home subscriber server (HSS)of the network based on the ESM information.

As further shown in FIG. 4, process 400 may include providing, to aserving gateway (SGW) of the network, the create session request thatincludes the indication (block 430). For example, the network device(e.g., using processor 320, storage component 340, communicationinterface 370, and/or the like) may provide, to a serving gateway (SGW)of the network, the create session request that includes the indication,as described above in connection with FIGS. 1A-2.

As further shown in FIG. 4, process 400 may include receiving, from theSGW and as a response to the create session request, a create sessionresponse that includes rules for handling the connection for the userdevice that is associated with the NAS and the particular interface, therules having been generated by a policy and charging rules function(PCRF) of the network (block 440). For example, the network device(e.g., using processor 320, communication interface 370, and/or thelike) may receive, from the SGW and as a response to the create sessionrequest, a create session response that includes rules for handling theconnection for the user device that is associated with the NAS and theparticular interface, as described above in connection with FIGS. 1A-2.In some implementations, the rules may have been generated by a policyand charging rules function (PCRF) of the network. In someimplementations, the rules may include access point name (APN) controlparameters.

As further shown in FIG. 4, process 400 may include providing, to theuser device and based on the create session response, an attach acceptthat includes the rules, to permit the user device is to connect withthe network and to utilize the rules based on the create sessionresponse (block 450). For example, the network device (e.g., usingprocessor 320, storage component 340, communication interface 370,and/or the like) may provide, to the user device and based on the createsession response, an attach accept that includes the rules, to permitthe user device to connect with the network and to utilize the rulesbased on the create session response, as described above in connectionwith FIGS. 1A-2. In some implementations, the network device may providethe attach accept that includes the rules to the base station to permitthe base station to cause the user device to connect with the networkand to utilize the rules based on the attach accept.

Process 400 may include additional implementations, such as any singleimplementation or any combination of implementations described belowand/or described with regard to any other process described herein.

Although FIG. 4 shows example blocks of process 400, in someimplementations, process 400 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 4. Additionally, or alternatively, two or more of theblocks of process 400 may be performed in parallel.

Some implementations described herein provide a network device thatenables different charging and policy enforcement for small data overNAS and an S11-U interface. For example, the network device may receivean attach request from a base station of a network, wherein the attachrequest may indicate that a user device is attempting a connectionassociated with a non-access stratum (NAS) and a particular interface.The network device may generate, based on the attach request, a createsession request that includes an indication that the connection for theuser device is associated with the NAS and the particular interface, andmay provide, to a serving gateway (SGW) of the network, the createsession request that includes the indication. The network device mayreceive, from the SGW and as a response to the create session request, acreate session response that includes rules for handling the connectionfor the user device that is associated with the NAS and the particularinterface, wherein the rules have been generated by a policy andcharging rules function (PCRF) of the network. The network device mayprovide, to the user device and based on the create session response, anattach accept that includes the rules, to permit the user device is toconnect with the network and to utilize the rules based on the createsession response.

The foregoing disclosure provides illustration and description, but isnot intended to be exhaustive or to limit the implementations to theprecise form disclosed. Modifications and variations are possible inlight of the above disclosure or may be acquired from practice of theimplementations.

As used herein, the term component is intended to be broadly construedas hardware, firmware, or a combination of hardware and software.

To the extent the aforementioned implementations collect, store, oremploy personal information of individuals, it should be understood thatsuch information shall be used in accordance with all applicable lawsconcerning protection of personal information. Additionally, thecollection, storage, and use of such information can be subject toconsent of the individual to such activity, for example, through wellknown “opt-in” or “opt-out” processes as can be appropriate for thesituation and type of information. Storage and use of personalinformation can be in an appropriately secure manner reflective of thetype of information, for example, through various encryption andanonymization techniques for particularly sensitive information.

It will be apparent that systems and/or methods, described herein, maybe implemented in different forms of hardware, firmware, or acombination of hardware and software. The actual specialized controlhardware or software code used to implement these systems and/or methodsis not limiting of the implementations. Thus, the operation and behaviorof the systems and/or methods were described herein without reference tospecific software code—it being understood that software and hardwaremay be designed to implement the systems and/or methods based on thedescription herein.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of possible implementations. In fact,many of these features may be combined in ways not specifically recitedin the claims and/or disclosed in the specification. Although eachdependent claim listed below may directly depend on only one claim, thedisclosure of possible implementations includes each dependent claim incombination with every other claim in the claim set.

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and may be used interchangeably with “one or more.” Furthermore,as used herein, the term “set” is intended to include one or more items(e.g., related items, unrelated items, a combination of related andunrelated items, etc.), and may be used interchangeably with “one ormore.” Where only one item is intended, the term “one” or similarlanguage is used. Also, as used herein, the terms “has,” “have,”“having,” or the like are intended to be open-ended terms. Further, thephrase “based on” is intended to mean “based, at least in part, on”unless explicitly stated otherwise.

What is claimed is:
 1. A network device, comprising: one or morememories; and one or more processors, communicatively coupled to the oneor more memories, to: receive an attach request from a base station of anetwork, the attach request indicating that a user device is attemptinga connection with the network for data transfer over a non-accessstratum (NAS) and a particular interface, the particular interfaceincluding an S11-U interface, and the user device including an Internetof Things (IoT) device; provide an evolved packet system (EPS) sessionmanagement (ESM) information request to the user device based on theattach request; receive ESM information from the user device based theESM information request; generate, based on the ESM information, acreate session request that includes an indication that the connectionfor the user device is intended for the NAS and the particularinterface; provide, to a serving gateway (SGW) of the network, thecreate session request that includes the indication; receive, from theSGW and as a response to the create session request, a create sessionresponse that includes rules for handling the connection for the userdevice that is intended for the NAS and the particular interface, therules having been generated by a policy and charging rules function(PCRF) of the network, the PCRF determining the rules for handling theconnection over the NAS and via the particular interface based on theindication; and provide, to the user device and based on the createsession response, an attach accept, that includes the rules, to permitthe user device to connect with the network and to utilize the rulesbased on the create session response.
 2. The network device of claim 1,wherein the one or more processors are further to: perform a locationupdate, associated with the network device, with a home subscriberserver (HSS) of the network based on the ESM information.
 3. The networkdevice of claim 1, wherein the one or more processors are further to:provide the attach accept that includes the rules to the base station topermit the base station to cause the user device to connect with thenetwork and to utilize the rules based on the attach accept.
 4. Thenetwork device of claim 1, wherein: the network device includes amobility management entity (MME) of the network.
 5. The network deviceof claim 1, wherein the indication includes an attribute value pair thatindicates the connection for the user device is intended for the NAS andthe particular interface, and the rules having been generated by thePCRF based on the attribute value pair.
 6. The network device of claim1, wherein the rules include access point name (APN) control parameters.7. The network device of claim 1, wherein the one or more processors arefurther to: perform a location update, associated with the networkdevice, with a home subscriber server (HSS) of the network based on theattach request, wherein the location update is used to one or more of:inform the HSS about an identity of the network device, update thenetwork device with user subscription data, or provide the HSS with userdevice service capability.
 8. A non-transitory computer-readable mediumstoring instructions, the instructions comprising: one or moreinstructions that, when executed by one or more processors of a networkdevice, cause the one or more processors to: receive an attach requestfrom a base station of a network, the attach request indicating that auser device is attempting a connection associated with a non-accessstratum (NAS) and a particular interface, the particular interfaceincluding an S11-U interface, and the user device including an Internetof Things (IoT) device; generate, based on the attach request, a createsession request that includes an indication that the connection for theuser device is associated with the NAS and the particular interface;provide, to a serving gateway (SGW) of the network, the create sessionrequest that includes the indication; receive, from the SGW and as aresponse to the create session request, a create session response thatincludes rules for handling the connection for the user device that isassociated with the NAS and the particular interface, the rules havingbeen generated by a policy and charging rules function (PCRF) of thenetwork, the PCRF determining the rules for handling the connection overthe NAS and via the particular interface based on the indication; andprovide, to the user device and based on the create session response, anattach accept that includes the rules, to permit the user device is toconnect with the network and to utilize the rules based on the createsession response.
 9. The non-transitory computer-readable medium ofclaim 8, wherein the instructions further comprise: one or moreinstructions that, when executed by the one or more processors, causethe one or more processors to: perform a location update, associatedwith the network device, with a home subscriber server (HSS) of thenetwork based on the attach request.
 10. The non-transitorycomputer-readable medium of claim 8, wherein the instructions furthercomprise: one or more instructions that, when executed by the one ormore processors, cause the one or more processors to: provide the attachaccept that includes the rules to the base station to permit the basestation to cause the user device to connect with the network and toutilize the rules based on the attach accept.
 11. The non-transitorycomputer-readable medium of claim 8, wherein the indication includes anattribute value pair that indicates the connection for the user deviceis associated with the NAS and the particular interface.
 12. Thenon-transitory computer-readable medium of claim 8, wherein theparticular interface is for tunneling of data associated with the NASfrom the user device.
 13. The non-transitory computer-readable medium ofclaim 8, wherein the instructions further comprise: one or moreinstructions that, when executed by the one or more processors, causethe one or more processors to: perform a location update, associatedwith the network device, with a home subscriber server (HSS) of thenetwork based on the attach request, wherein the location update is usedto one or more of: inform the HSS about an identity of the networkdevice, update the network device with user subscription data, orprovide the HSS with user device service capability.
 14. A method,comprising: receiving, by a network device, an attach request from afirst device of a network, the attach request indicating that a userdevice is attempting a connection associated with a non-access stratum(NAS), the user device including an Internet of Things (IoT) device;generating, by the network device and based on the attach request, acreate session request that includes an indication that the connectionfor the user device is associated with the NAS; providing, by thenetwork device and to a second device of the network, the create sessionrequest that includes the indication; receiving, by the network device,from the second device, and as a response to the create session request,a create session response that includes rules for handling theconnection for the user device that is associated with the NAS, therules having been generated by a policy and charging rules function(PCRF) of the network, the PCRF determining the rules for handling theconnection over the NAS and via a particular interface based on theindication, the particular interface including an S11-U interface; andproviding, by the network device, to the user device, and based on thecreate session response, an attach accept that includes the rules. 15.The method of claim 14, wherein the user device is to connect with thenetwork and to utilize the rules based on the create session response.16. The method of claim 14, further comprising: providing an evolvedpacket system (EPS) session management (ESM) information request to theuser device based on the attach request; receiving ESM information fromthe user device based on the ESM information request; and generating thecreate session request based on the ESM information.
 17. The method ofclaim 14, further comprising: providing the attach accept that includesthe rules to the first device of the network to permit the first deviceto cause the user device to connect with the network and to utilize therules based on the attach accept.
 18. The method of claim 14, whereinthe indication includes an attribute value pair that indicates theconnection for the user device is associated with the NAS.
 19. Themethod of claim 14, further comprising: performing a location update,associated with the network device, with a home subscriber server (HSS)of the network based on the attach request, wherein the location updateis used to one or more of: inform the HSS about an identity of thenetwork device, update the network device with user subscription data,or provide the HSS with user device service capability.
 20. The methodof claim 14, wherein the network device includes a mobility managemententity (MME) of the network.